home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Internet
/
Collection of Internet.iso
/
infosrvr
/
doc
/
www_talk.arc
/
000314_timbl@www3.cern.ch _Thu Nov 12 17:10:25 1992.msg
< prev
next >
Wrap
Internet Message Format
|
1992-11-30
|
4KB
Return-Path: <timbl@www3.cern.ch>
Received: from dxmint.cern.ch by nxoc01.cern.ch (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
id AA06590; Thu, 12 Nov 92 17:10:25 MET
Received: by dxmint.cern.ch (dxcern) (5.57/3.14)
id AA06372; Thu, 12 Nov 92 17:23:13 +0100
Received: by www3.cern.ch (NX5.67c/NX3.0S)
id AA03876; Thu, 12 Nov 92 17:19:16 +0100
Date: Thu, 12 Nov 92 17:19:16 +0100
From: Tim Berners-Lee <timbl@www3.cern.ch>
Message-Id: <9211121619.AA03876@www3.cern.ch>
Received: by NeXT.Mailer (1.87.1)
Received: by NeXT Mailer (1.87.1)
To: Edward Vielmetti <emv@msen.com>
Subject: Re: proposed registration of type 'text/html' for MIME
Cc: www-talk@nxoc01.cern.ch
Reply-To: timbl@nxoc01.cern.ch
> Here's the form for registering 'text/html' partly filled in, from RFC
> 1341.
> I don't think this needs a ton of work, just to fill in a few of the
> references. As we get some operations experience with it (and some
> applications support!) I could imagine putting more frobs on it. Not
> yet tho.
OK, good idea. Here is a 2nd draft. I have changed:
We restrict it to 7 bit, any 8 bit use is cheating and causes unpredictable
things to happen. SGML provides for funny character encoding like é and
things. We could also make the base character set a parameter (for the Fins).
Should we put a limit on line length? Do we need one to prevent an
encoding system from being mandatory for all HTML documents?
I have put a ref to the HTML spec rather than the HTTP spec. I'll
upgrade that to include the DTD and make it more RFCish (70 characters wide and
stuff ;-)
_______________________________________________________
To: IANA@isi.edu
Subject: Registration of new MIME content-type/subtype text/html
MIME type name:
text
MIME subtype name:
html
Required parameters:
none
Optional parameters:
left open for future study.
Any additional parameters should match up with existing HTML
constructs, so that e.g. the parameter
title="Making links in the web"
would be functionally equivalent to an HTML preamble of
<title>Making links in the web</title>
Encoding considerations:
HTML text should be restricted to ASCII printable characters
unless an extended character set is specfified in an
optioinal parameter (subject for future study). There is no
limit on line length.
Security considerations:
HTML documents may contain embedded information used to
instruct browsers and viewers to execute queries on remote
databases. Some HTML browsers have included support for
embedded command languages. Such facilities should be used
with care.
Published specification:
"Hypertext Markup Language", Tim Berners-Lee, CERN, 1992.
available as http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html
or as by anonymous FTP from ftp://info.cern.ch/pub/doc/www/html.txt
See also:
"The HTTP Protocol as Implemented in W3", avaiable for
anonymous ftp from ftp://info.cern.ch/pub/doc/www/http.txt.
Describes the HTTP interactive access protocol and the tags used
in HTML documents.
"The WWW Book", from
ftp://info.cern.ch/pub/doc/the_www_book.txt.
"Universal Document Identifiers on the Network", OSI-DS-XXX,
available by anonymous FTP from
ftp://info.cern.ch/info.cern.ch/pub/www/doc/url3.{txt,ps}.
Person & email address to contact for further information:
Tim Berners-Lee, CERN, 1211 Geneva 23, Switzerland
timbl@info.cern.ch